https://docs.goquorum.consensys.net/en/stable/Concepts/Privacy/PrivateTransacti

onLifecycle/)

In this scenario, where Org A, Org B, and Org C are working

together in a Quorum network that is being represented through

their nodes A, B, and C respectively. While Org A wishes to

execute a transaction with Org B, it doesn’t wish to involve Org

C in the same. Now, let’s explore how the entire flow of the data

would look like.

Org A now sends a transaction to its own node with the

instructions in the associated transaction payload. The payload

has a property “privateFor” where it includes the public keys of

all the nodes with which the transaction must be shared. In the

current scenario, “privateFor” property would have the public

keys of Org A and Org B and not Org C. Having its own public

key, however, is optional for this property.

Node A’s transaction manager now shares the transaction with

its own Enclave. The latter encrypts the transaction payload in

such a way that only the rightful owner can decrypt it with its

own private key. The encrypted transaction now is stored and

shared back to the node A’s transaction manager by the

Enclave.

Transaction manager now propagates the transaction in the

entire network using P2P protocol. The transaction now

packaged in a block reaches every participating node in the

network.

Only the nodes that are the rightful receiver can receive the

encrypted transaction through the transaction manager and get

it decrypted through the private keys stored in their Enclave.

15.4 Industry Adoption

Quorum has many implementations across business verticals which

are in PoC, pilot, or in production stage. The most popular project

called “JPM Coin” crafted by JP Morgan was introduced for instant

settlement between the JP Morgan’s clients from different parts of

the globe. Project Ubin is another very popular project by Monetary